Canonical plan for making Gobby hooks work across Claude/Codex/Gemini/
QwenCode sandboxes. Introduces a new ghook crate as the fourth member
of this workspace (alongside gcode, gsqz, gloc), plus runtime-detection
on the Python daemon side so the two repos can ship independently.

Companion task: gobby #11843 (bootstrap) and gobby #11842 (cleanup
follow-up to remove the legacy hook_dispatcher.py path once ghook is
universal.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
EOF
)

PR 1 of the sandbox-tolerant-hooks Rust migration (R2-01 + R2-04 + R2-05).
Scaffolds the shared gobby-core lib and ports find_project_root and
read_project_id as public API. gcode keeps its local copy until PR 4
(R2-08) to keep this diff behavior-free. See
docs/plans/sandbox-tolerant-hooks-rust.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Ports hook_dispatcher.py:145-175 port-resolution into `bootstrap` + a
new `daemon_url` module. Reads `daemon_port` and `bind_host` from
`~/.gobby/bootstrap.yaml`; falls back to 60887 and 127.0.0.1 on missing
or malformed files. `daemon_url` normalizes wildcard listen addresses
(`0.0.0.0`, `::`, `::0`) to `127.0.0.1` for dialing — the dispatcher and
gcode both silently broke when users set `bind_host: 0.0.0.0`.

13 unit tests cover default fallback, malformed YAML, custom port/host,
and wildcard normalization. No consumers yet — ghook (PR 3) is first.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…atch

Port hook_dispatcher.py to a native Rust binary with enqueue-first
semantics: every invocation writes an envelope to
~/.gobby/hooks/inbox/<p>-<ts13>-<uuid>.json (fsync + rename) before the
daemon POST, so sandbox FS-read denials and transient network failures
never drop a hook — the drain worker replays from disk.

CLI: --gobby-owned, --diagnose, --version. Exit 0 on success or
non-critical failure (enqueued); 2 on critical failure (enqueued,
signals host CLI). Malformed stdin goes directly to inbox/quarantine/
with a .meta.json sidecar (reason, json_error, stdin_bytes_b64) —
drain never replays quarantined envelopes.

Headers (X-Gobby-Project-Id, X-Gobby-Session-Id) are omitted entirely
when unknown — never empty strings. Walk-up for project context runs
before detach on Unix (setsid). Windows detach uses FreeConsole(); the
spawn-time flags in the plan cannot be self-applied to a running
process, and the enqueue-first file is the source of truth regardless.

Terminal-context enrichment gated by per-CLI hook set; TMUX_PANE only
emits when TMUX is also set to avoid parent/child pane confusion.

Schemas frozen at v1 (inbox-envelope, diagnose-output), validated in
unit tests. Release workflow mirrors release-gcode with tag prefix
gobby-hook-v*; publishes to crates.io as gobby-hook.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…lpers

Remove duplicate find_project_root and read_project_id from gcode, now importing
them from gobby_core::project. Updates call sites in config.rs and commands/index.rs.
Deletes redundant tests (now tested in gobby-core). Adds gobby-core as a path
dependency.

Validation:
- crates/gcode/Cargo.toml adds gobby-core path dependency
- find_project_root and read_project_id removed from crates/gcode/src/project.rs
- Call sites updated to import from gobby_core::project
- Tests removed (behavior tested in gobby-core)
- cargo test --workspace: PASS (148 tests)
- cargo clippy --workspace --all-targets -- -D warnings: PASS
- cargo fmt --all --check: PASS

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Mirrors updates made to the Python-side sandbox-tolerant-hooks-rev1
plan after the gobby-cli Phase 2 review:

- Windows detach spec corrected: `FreeConsole()` is the post-spawn
  analog; `DETACHED_PROCESS | CREATE_NEW_PROCESS_GROUP` are
  CreateProcess parent-side flags and cannot be self-applied from the
  already-spawned child. Updated in both PR 3 description and the
  contract-resolution section.
- Crate & distribution: documents the gobby-core → ghook publish-order
  constraint, with the `version` + `path` dep declaration pattern that
  lets workspace builds and crates.io both resolve.
- PR 3 CI bullet: explicit note that `release-gobby-core.yml` must
  land in the repo first and the first `ghook` release is gated on
  the matching `gobby-core` version being live on the registry.
- Empty-stdin normalization: ghook treats empty as `input_data = {}`;
  dispatcher exits non-zero. Documented transition-window divergence;
  exit code still governed by `--critical`, no silent drop.
- POST body shape: daemon endpoint accepts both legacy bare and
  schema-v1 envelope. Python plan's §2.8 adds a handler test to pin
  the tolerance.

…es on crates.io success

gobby-hook depends on gobby-core as a path dep with a version; the release
flow requires gobby-core to exist on crates.io first, so add a library-only
release workflow keyed on gobby-core-v* tags. Also tighten release-gcode and
release-ghook so the GitHub Release job waits on the crates.io step —
prevents the footgun where binaries ship with a version that failed upstream.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…s/gobby-core → crates/gcore

Two pre-release naming fixes, landed together while nothing is on crates.io
yet so the rename is free:

(A) Package gobby-hook → gobby-hooks. Binary (ghook), crate dir (crates/ghook),
    and schema IDs unchanged. Convention: plural package name for domain
    families (gobby-hooks, future gobby-tasks), singular binary for the tool
    (ghook, gtask). Release tag prefix becomes gobby-hooks-v*.

(B) Directory crates/gobby-core → crates/gcore to match the g-prefix short-name
    pattern (gcode, gsqz, gloc, ghook). Package name stays gobby-core — only
    the filesystem layout changed. Workflow renamed release-gobby-core.yml →
    release-gcore.yml for consistency with the other release-<short>.yml files.

Verified: cargo fmt, cargo clippy --workspace --all-targets -- -D warnings,
cargo test --workspace (267 passing), YAML syntax on all workflow files.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…n fts.rs LIKE escape

Extract empty_response_for_unresolved helper in commands/graph.rs and use it
from callers/usages/blast_radius. resolve_symbol_name in search/fts.rs no
longer includes the resolved name in its suggestions vec — callers get only
alternatives. LIKE fallback now escapes %/_/\ via new escape_like helper and
uses ESCAPE '\' so symbol names containing underscores (snake_case) match
literally. glob_to_like_prefix refactored to reuse escape_like; behavior
unchanged for existing callers.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…040)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…0.1.0, ghook 0.1.0

Bump crate versions, add new ghook user/dev guides and gcore dev
guide, note gobby-core dependency in gcode dev guide and low-savings
marker suppression in gsqz user guide, add four versioned CHANGELOG
sections, and surface ghook + gcore in the top-level README.

Adds version="0.1" to gcode's path dep on gobby-core so the manifest
is valid for crates.io upload. Staged release order: tag gcore-v0.1.0
first (so gobby-core lands on the registry), then tag gcode-v0.6.0,
gsqz-v0.4.1, ghook-v0.1.0 together.

Verified: cargo build/test/clippy/fmt all clean across the workspace
(267 tests passing). cargo package -p gobby-core succeeded;
gobby-code packaging waits on gobby-core being on the registry
(expected -- release ordering handles this).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…o-op strategy

Follow-up to #111. The inner [gsqz:low-savings] marker is suppressed
when adding it would grow output, but the outer
"[Output compressed by gsqz -- STRATEGY, X% reduction]" header was
still being prepended for the resulting */no-op strategy. That's
noise -- no compression actually happened, so the header is just
spurious.

Adds CompressionResult::is_passthrough() classifying passthrough,
excluded, and */no-op together. main.rs now uses it for both the
outer-header decision and the daemon savings report so the two stay
in sync. Adds a unit test for the classification and asserts the
existing low-savings-suppressed test result also reports as
passthrough.

Rolls into the unreleased 0.4.1 -- no version bump. Tests: 149 in
gsqz (+1 new), 268 across the workspace, all passing. Verified
end-to-end: the compound-git command that previously emitted
"git-mutation/low-savings, -1% reduction" now emits clean original
output (strategy=git-mutation/no-op, savings=0.0%, no header).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ry_sort_by

Two pre-existing call sites in crates/gsqz/src/primitives/group.rs
trigger Rust 1.95.0's new clippy::unnecessary_sort_by lint. Local
toolchain is 1.94 so they slipped through; CI runs 1.95 and rejects
them. Mechanical replacement of

    sort_by(|a, b| b.1.len().cmp(&a.1.len()))

with

    sort_by_key(|b| std::cmp::Reverse(b.1.len()))

at lines 373 and 414. No behavior change. Rolls into the unreleased
gsqz 0.4.1 -- no version bump, no CHANGELOG entry (this is a CI
correctness fix, not a user-facing change).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ble_match

crates/gcode/src/commands/init.rs:34 trips clippy::collapsible_match
on a nested `match Err(e) => { if !quiet { ... } }`. Convert to a
match guard `Err(e) if !quiet => { ... }`; the `_ => {}` arm catches
the quiet=true case as before, so behavior is preserved.

Updated local toolchain to 1.95 (was 1.94) so all 1.95 lints fire
locally going forward. Verified all five CI clippy commands pass on
1.95: gobby-core, gobby-hooks, gobby-squeeze, gobby-local,
gobby-code (no embeddings). Rolls into unreleased gcode 0.6.0 -- no
version bump.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…e 0.1.1

ghook 0.1.0 published to crates.io but the Windows build target
failed: edition 2024 requires `extern "system" { ... }` to be
`unsafe extern "system" { ... }`. Local Mac dev never exercised the
#[cfg(windows)] branch in detach.rs so it slipped through.

Fix is one line in crates/ghook/src/detach.rs:36 plus a Cargo.toml
bump to 0.1.1 and a CHANGELOG entry. Linux/Mac use the
#[cfg(unix)] setsid(2) branch and were never affected -- the
crates.io 0.1.0 install works on those platforms but not Windows.

Verified: cargo build/test/clippy clean (27 ghook tests passing).
Once gobby-hooks-v0.1.1 is tagged, the Release ghook workflow
should succeed across all 5 build targets and create the GitHub
Release that 0.1.0 missed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>